Overview
Menu Management (MM) has developed an integration with Aztec that will allow Zonal customers to use Menu Management product. Aztec uses the data provided by the MM XML file upload to update Aztec database to avoid a need for re-keying data in two systems.
This topic is intended to provide an overview of possible data errors that will stop the data export from Menu Manager and actions that must take place to correct them.
Invalid Data Errors
|
Error |
Action Required |
|---|---|
|
Recipe with no valid ingredients |
Each ingredient of the provided recipe must be checked. The user needs to make sure that the ingredient is active, and it has been configured with all Can Order flags to all for the export. |
|
Recipe with no dispense size multiple |
This error should be escalated to the dev team as it cannot be fixed on UI |
|
Choice has options/s that are not valid |
All the options within the listed choice have to be checked. The option must be active, published and has at least one ingredient |
|
Alternative standard Line recipe without main standard Line item |
A standard line ingredient has to be added to the alternative portion. |
|
Supplier Items with the same product code |
The product codes within one supplier must be unique. The product code must be changed for the stock items listed in the error. Please note that this also applies to any inactive products |
|
Supplier Items with the same supplier and pack size |
The stock item cannot have more then one supplier product with the same pack size from the same supplier. The user must make one of these product inactive
|
|
Stock items linked to categories that don’t exist in Aztec |
This rule was created as a precaution. MM users do not have the access to add new Stock Categories in MM. If that should happen the fix is to change the reporting category for the affected item to an Aztec category and make the MM category inactive |
|
Recipes linked to categories that don’t exist in Aztec |
This rule was created as a precaution. MM users do not have the access to add new Recipe Categories in MM. If that should happen the fix is to change the reporting category for the affected recipe to an Aztec category and make the MM category inactive |
|
Stock item has no pack size set to reporting size |
This rule was created as a precaution. Each stock item by default will have one pack size selected as a reporting size. This could only be caused by the bug on the system. The fix would be to apply the reporting flag to one of the pack sizes |
|
Batch has no pack size set to reporting size |
The pack size has to be added for each batch as it is being sent to Aztec as a counting unit for Prep item. The pack size within that back has to match the family unit of the batch stock size |
|
Ingdts in alt recipes not in std recipe |
There is an ingredient that is used in alternative portion recipe, but it is not added to the standard portion recipe. There is a rule that was introduces which inserts the unique ingredient used in an alternative portion recipe into the standard portion recipe at 0 quantity and the RB flag in not applied (this ingredient will not be included in the recipe book reports). The user however manually delete the 0qty ingredient from the standard portion recipe and if it is still used in alternative portion recipe this will give us an error |
|
A supplier product is missing a default star, one per supplier |
The default supplier star must be applied to one supplier product for each supplier used within a stock item |